Skip to content

[proposal] Allow 0 to be a valid UNIX timestamp.#1579

Open
falconscript wants to merge 2 commits intobalderdashy:masterfrom
falconscript:patch-1
Open

[proposal] Allow 0 to be a valid UNIX timestamp.#1579
falconscript wants to merge 2 commits intobalderdashy:masterfrom
falconscript:patch-1

Conversation

@falconscript
Copy link

Issuing console warnings for timestamp of 0 isn't necessary and are sometimes used to represent "unset" programmatically since datetimes must be type 'ref' and 'ref' cannot be null. Removing the if check will allow them to pass through in auto-migrations without spurring messages.

Issuing console warnings for timestamp of 0 isn't necessary and are sometimes used to represent "unset" programmatically since datetimes must be type 'ref' and 'ref' cannot be null. Removing the if check will allow them to pass through in auto-migrations without spurring messages.
@sailsbot
Copy link

Hi @falconscript! It looks like your pull request title doesn’t quite conform to our guidelines. Please edit the title so that it starts with [proposal], [patch], [fixes #], or [implements #]. Once you've fixed it, post a comment below (e.g. "ok, fixed!") and we'll take a look!

@falconscript falconscript changed the title Allow 0 to be a valid UNIX timestamp. [proposal] Allow 0 to be a valid UNIX timestamp. Oct 17, 2018
@falconscript
Copy link
Author

[proposal] Added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants